The SAS 9.2 Depot Subsetting Utility enables you to create a subsetted depot of selected SAS® 9.2 Foundation products and SAS® 9.2 clients from your SAS® 9.2 master depot. The subsetted depot is projected to be smaller in size than your master depot because it has fewer SAS products in the products directory of the subsetted depot.
Important: The SAS® 9.2 Depot Subsetting Utility should only be used with SAS® 9.2 depots. Do not use this utility with SAS® 9.3 depots.
The following table provides a list of the most commonly installed clients and required components, their corresponding software codes, and the approximate amount of depot space that is required for each product.
SAS® Client | Software Code |
Approximate Size |
---|---|---|
SAS Client Connection Profile Configuration | clientconfig | 7.3M |
SAS® Enterprise Guide® | eguide | 310M |
SAS® Enterprise Miner Clients
SAS® Enterprise Miner SAS® Enterprise Miner Client Configuration SAS® Enterprise Miner Java Client SAS® Enterprise Miner Thin Client Configuration SAS® Enterprise Miner Plug-In for SAS Managment Console |
dmine dmineclntcfg dmineclient dminethincfg dminesmc |
614M |
SAS® Data Integration Studio | databuilder | 270M |
SAS® Forecast Server Clients
SAS® Forecast Studio SAS® Forecast Server Plug-In for SAS Management Console |
forcaststdo forecastsmc |
375M
(135M) (240M) |
SAS® Information Map Studio | mapcenter | 220M |
SAS® Management Console | mgmtconsole | 240M |
SAS® Personal Login Manager | mrloginmgr | 210M |
SAS® Add-In for Microsoft Office | msofficeint | 285M |
SAS® OLAP Cube Studio | olapserver | 285M |
SAS® Text Miner Java Client | tmclient | 9M |
System Requirements for SAS® Enterprise Guide® and SAS® Add-In for Microsoft Office [1] | sysreqwizard | 567M |
*Report Fonts for Clients | ttfontsvert | 220M |
[1] Must be included with SAS Enterprise Guide and the SAS Add-In for Microsoft Office |
To project the size of the client products in a subsetted depot, add 1.43GB (1,430MB) to the sum of the sizes for all products that are to be included. For example, if your organization licenses SAS Enterprise BI Server plus SAS Enterprise Guide, the size of your subsetted client depot would be approximately 3.55GB or 1.43GB + 2.12GB. The corresponding software codes for SAS Enterprise BI Server clients plus SAS Enterprise Guide are as follows:
eguide mapcenter mgmtconsole msofficeint mrloginmgr olapserver sysreqwizard |
To project the size of the SAS Foundation products in a subsetted depot, see the "Space Requirements" sections in System Requirements for SAS 9.2® Foundation for Microsoft Windows and System Requirements for SAS® 9.2 Foundation for Microsoft Windows for x64.
The following section discusses the steps that are involved with using the Depot Subsetting Utility:
From media or by download, create a SAS Software Depot that will be the master depot to be used as the source from which to create the subsetted depot.
Using Windows Explorer, you can create the directory where the subsetted products will be placed or you can create that directory by clicking Create New Folder using the Depot Subsetting Tool.
The user ID that is used to run the depot subsetting utility must have
You can extract the utility to any location. It can reside locally or remotely from the master or target depot locations.
Three .txt files are made available to you that list the SAS clients and products:
You must correctly configure whichever .txt file you need to ensure that you place the correct SAS products in your subsetted depot.
You can point to any one of these three .txt files when you start creating the subsetted depot.
Select wanted products by removing the pound sign (#) in front of that product that comments out that selection. In the screenshot below, non-SAS Enterprise Miner products have # signs in front of them and thus will not be placed in the subsetted depot.
Note: To include the SAS Text Miner Client in the subsetted depot, in the SASDepotSubset.txt file you must include both software codes tmclient and tmine.
Not all SAS Foundation products and SAS clients need to be copied to the subsetted depot and are optional. However, they will be copied if they exist in the master depot and you have specified them in the .txt file that you choose during the subsetting process. You can include any combination of SAS Foundation products or SAS clients in the subsetted depot.
Note: Some products are required and must be installed for SAS clients or SAS Foundation products to work properly. They are listed in the section entitled:
############################################################################# # The following is a list of products you should always include in your # Foundation depot if the products exist in the order being subset. ############################################################################# ############################################################################# # The following is a list of products you should always include in your # client depot if the products exist in the order being subset. ############################################################################# ############################################################################# # The following is a list of Threaded Kernel products you should include in # your depot when required by a Foundation product you have chosen to # include in your depot. Please see the notes in the Foundation product # list to determine which of the following Threaded Kernel products to # uncomment, if any. #############################################################################
Select an operating system from your order.
Note that if you specify no operating system, the utility copies files for all operating systems found in the master depot to the subsetted depot. Here are examples of operating systems:
You can run the Subsetting Depot Tool by
The utility starts copying from the source master depot directory to the target subset depot directory.
When the utility creates the subsetted depot successfully, this dialog box appears:
Note: You can run multiple instances of the Subsetting Depot Tool, for example:
Note: The product directory of the newly subsetted depot will contain fewer products than the master depot as shown in the following display:
Here is the syntax that is used for running the Depot Subsetting Utility via a DOS command prompt. The parameters are defined as follows, and they are all required:
-o (order number) –i (input SAS Software Depot Directory [master]) -d (output SAS Software Depot directory [client]) -p (input file containing 12-Byte product names to copy from the master depot) -s (operating systems which are to be included in the output SAS Software Depot. If specifying more than one operating system, separate the values with a single space.) -v (verbose, optional)
The following is sample syntax:
No dialog boxes appear unless a mistake has been made in the syntax. Here are several typical error message that might appear:
No dialog boxes appear when you run the SASDepotSubset.exe via a DOS prompt unless the syntax is faulty, a parameter is missing and the subsetting utility prompts you for the missing parameter, or a non-syntax error occurs.
After successfully creating the subsetted depot, the log opens for your inspection.
You can also find the SASDepotSubset.log in the subsetted depot:
With the subsetted depot, you can now burn media, copy the depot to other locations, or install the SAS Foundation products and SAS clients.
You can only place SAS Foundation products and SAS clients from one order in a subsetted depot; the utility does not currently support SAS Foundation products and SAS clients from multiple orders in the same depot.
Once you have created a subsetted SAS Software Depot, you will not be permitted to place another set of SAS Foundation products and SAS clients in the depot or download any order (including maintenance) to the subsetted SAS Software Depot.
If you want to create a subsetted depot of maintenance for SAS Foundation products and SAS clients, you will need to create a master depot of a maintenance order and then run the subsetting utility against the newly created master depot. The result will be a separate subsetted SAS Software Depot with the selected SAS Foundation product and SAS client product set with maintenance.
You cannot use the depot subsetting utility to subset any languages. That functionality is projected for a later release of SAS.
See SAS note 39212 "Using the SAS® 9.2 Depot Subsetting Utility to create SAS Clients-only depots in the UNIX environment" for creating subsetted depots of clients in a UNIX operating environment.
When you use the SAS Depot Subsetting Utility, error messages similar to these might appear:
ERROR: Expected file does not exist or cannot be read from master depot D:\SAS Software Depot\sid_files\SAS92_623952_50305016_Win_Server.txt" size="1738" time="20100921063531" checksum="665ca19293bbd6ffc75676ee87f58a63. SASDepotSubset cannot proceed. ERROR: D:\SAS Software Depot\sid_files\SAS92_623952_50305016_Win_Server.txt" size="1738" time="20100921063531" checksum="665ca19293bbd6ffc75676ee87f58a63 does not exist or cannot be read. The master depot may be corrupt. ERROR: Processing has stopped. WARNING: The following products were NOT copied to the subset depot because they were either not found in this order or not found for any operating systems specified: securejava 478 directories were created or copied. 2561 files were created or copied. 1 error(s) were encountered.
To resolve these errors make sure the newest release of the SAS Depot Subsetting Utility is being used. The current release of the Subsetting Utility is 2.0 which can be verified in the SASDepotSubset.log file at the top as shown below. The SAS Depot Subsetting Utility 2.0 is available via the Downloads tab at the top of this page.
Note that subsetting an already subsetted depot is not supported. When you attempt to subset a subsetted depot, this error message appears:
Product Family | Product | System | SAS Release | |
Reported | Fixed* | |||
SAS System | N/A | Windows 7 Ultimate x64 | 9.2 TS2M2 | 9.3 TS1M0 |
Windows 7 Ultimate 32 bit | 9.2 TS2M2 | 9.3 TS1M0 | ||
Windows 7 Professional x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
Windows 7 Professional 32 bit | 9.2 TS2M2 | 9.3 TS1M0 | ||
Windows 7 Enterprise x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
Windows 7 Enterprise 32 bit | 9.2 TS2M2 | 9.3 TS1M0 | ||
Microsoft Windows Server 2008 | 9.2 TS2M2 | 9.3 TS1M0 | ||
Windows Vista | 9.2 TS1M0 | 9.3 TS1M0 | ||
Microsoft Windows XP Professional | 9.2 TS1M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Standard Edition | 9.2 TS1M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS1M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS1M0 | 9.3 TS1M0 | ||
Microsoft® Windows® for x64 | 9.2 TS1M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS1M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS1M0 | 9.3 TS1M0 | ||
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS1M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 for x64 | 9.3 TS1M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2008 for x64 | 9.3 TS1M0 | 9.3 TS1M0 | ||
Windows 7 Home Premium 32 bit | 9.3 TS1M0 | 9.3 TS1M0 | ||
Windows 7 Home Premium x64 | 9.3 TS1M0 | 9.3 TS1M0 | ||
Windows Vista for x64 | 9.3 TS1M0 | 9.3 TS1M0 |
Type: | Installation Note |
Priority: | high |
Date Modified: | 2012-07-25 09:47:01 |
Date Created: | 2010-03-22 13:14:57 |